Proving physical possession of internet-of-things (iot) devices

ABSTRACT

Disclosed herein are system, apparatus, article of manufacture, method and/or computer program product embodiments, and/or combinations and sub-combinations thereof, for determining physical possession of one or more IoT devices. According to some embodiments, a method for determining physical possession of a plurality of Internet-of-Things (IoT) devices includes determining physical possession of a first IoT device of the plurality of IoT devices. The method further includes determining whether the first IoT device with the determined physical possession satisfies a condition. In response to determining that the first IoT device with the determined physical possession does not satisfy the condition, determining physical possession of a second IoT device of the plurality of IoT devices. In response to determining that the first IoT device with the determined physical possession satisfies the condition, determining the physical possession of the plurality of IoT devices based on the determined physical possession of the first IoT device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. Pat. Application No.17/500,005, filed Oct. 13, 2021, which is herein incorporated byreference in its entirety.

BACKGROUND Field

This disclosure is generally directed to Internet-of-Things (IoT)devices, and more particularly to embodiments for proving physicalpossession of IoT devices.

Background

For a user of an IoT device to be able to configure and/or control theIoT device, the user often must prove ownership of the IoT device. Insome examples, physical possession of the IoT device by the user canestablish ownership of the IoT device by the user. In some IoT devices,one approach for proving physical possession can include using aphysical button on the IoT device. When the user presses and holds thephysical button for a given period of time, the IoT device resets to afactory-reset state. After that operation, the first messages to arriveat the IoT device will be trusted by the IoT device to communicate theidentity of the owner.

However, as discussed in more detail below, there may be differentstates or levels of ownership and/or physical possession. Each level ofownership and/or physical possession can have different requirements toprove physical possession.

SUMMARY

Provided herein are system, apparatus, article of manufacture, methodand/or computer program product embodiments, and/or combinations andsub-combinations thereof, for determining and/or proving physicalpossession of one or more IoT devices.

According to some embodiments, a computer implemented method fordetermining physical possession of a plurality of Internet-of-Things(IoT) devices includes determining physical possession of a first IoTdevice of the plurality of IoT devices. The method further includesdetermining whether the first IoT device with the determined physicalpossession satisfies a condition. In response to determining that thefirst IoT device with the determined physical possession does notsatisfy the condition, determining physical possession of a second IoTdevice of the plurality of IoT devices. In response to determining thatthe first IoT device with the determined physical possession satisfiesthe condition, determining the physical possession of the plurality ofIoT devices based, at least, on the determined physical possession ofthe first IoT device.

In some embodiments, in response to determining that the first IoTdevice with the determined physical possession does not satisfy thecondition, the method further includes determining whether the secondIoT device with the determined physical possession satisfies thecondition. In response to determining that the second IoT device withthe determined physical possession satisfies the condition, determiningthe physical possession of the plurality of IoT devices based on thedetermined physical possession of the second IoT device.

In some embodiments, determining the physical possession of the firstIoT device includes transmitting, using the first IoT device, a firstradio frequency (RF) packet to a user device, receiving, using the firstIoT device, a second RF packet from the user device, and determining thephysical possession of the first IoT device based on the second RFpacket received from the user device.

In some embodiments, determining the physical possession of the firstIoT device includes transmitting, using the first IoT device, a firstnear-field communication (NFC) packet to a user device, receiving, usingthe first IoT device, a second NFC packet from the user device, anddetermining the physical possession of the first IoT device based on thesecond NFC packet received from the user device.

In some embodiments, determining the physical possession of the firstIoT device includes receiving, using the first IoT device, a signal froma user device, determining, using the first IoT device, informationassociated with the received signal, and comparing, using the first IoTdevice, the determined information with predetermined information. Themethod further includes determining the physical possession of the firstIoT device based on the determined information matching with thepredetermined information. In some examples, the signal includes atleast one of an audio signal, a visible light signal, an infrared lightsignal, or a laser signal.

In some embodiments, determining the physical possession of the firstIoT device includes determining location information associated with thefirst IoT device, determining location information associated with auser associated with the first IoT device, and comparing the locationinformation associated with the first IoT device and the locationinformation associated with the user. The method further includesdetermining the physical possession of the first IoT device in responseto the location information associated with the first IoT devicematching the location information associated with the user.

In some embodiments, determining the physical possession of the firstIoT device includes capturing, using the first IoT device, an imagedisplayed on a user device, comparing, using the first IoT device, thecaptured image with a predetermined image, and determining the physicalpossession of the first IoT device based on the captured image matchingwith the predetermined image.

In some embodiments, determining the physical possession of the firstIoT device includes measuring, using the first IoT device, anacceleration force applied to the first IoT device and determining thephysical possession of the first IoT device based on the measuredacceleration force.

In some embodiments, determining the physical possession of the firstIoT device includes emitting, using the first IoT device, a first signalgenerated based on a predetermined code, receiving, using the first IoTdevice, a second signal, and determining, using the first IoT device, acode from the second signal. The method further includes comparing thedetermined code with the predetermined code and determining the physicalpossession of the first IoT device based on the determined code matchingwith the predetermined code.

According to some embodiments, a non-transitory computer-readable mediumincludes instructions stored thereon that, when executed by at least onecomputing device, cause the at least one computing device to performoperations for determining physical possession of a plurality ofInternet-of-Things (IoT) devices. The operations include determiningphysical possession of a first IoT device of the plurality of IoTdevices. The operations further include determining whether the firstIoT device with the determined physical possession satisfies acondition. In response to determining that the first IoT device with thedetermined physical possession does not satisfy the condition,determining physical possession of a second IoT device of the pluralityof IoT devices. In response to determining that the first IoT devicewith the determined physical possession satisfies the condition,determining the physical possession of the plurality of IoT devicesbased, at least, on the determined physical possession of the first IoTdevice.

According to some embodiments, an Internet-of-Things (IoT) deviceincludes a transceiver configured to communicate over a wireless networkand a physical possession determining system. The physical possessiondetermining system is configured to determine physical possession of theIoT device using at least one of transmitting a first signal to a userdevice, the first signal generated based on predetermined informationshared between the IoT device and the user device or receiving a secondsignal from the user device, the second signal generated based on thepredetermined information shared between the IoT device and the userdevice.

In some embodiments, the IoT device further includes a magnetic detectorconfigured to detect a presence of a magnet to determine the physicalpossession of the IoT device.

In some embodiments, the first signal includes a first radio frequency(RF) packet and the second signal includes a second RF packet. Thephysical possession determining system is configured to determine thephysical possession of the IoT device based on the second RF packetreceived from the user device.

In some embodiments, the second signal includes at least one of an audiosignal, a visible light signal, an infrared light signal, or a lasersignal. The physical possession determining system is further configuredto determine information associated with the second signal, compare theinformation associated with the second signal with the predeterminedinformation, and determine the physical possession of the IoT devicebased on the information associated with the second signal matching withthe predetermined information.

In some embodiments, the IoT device further includes one or morebuttons. The physical possession determining system is configured todetermine that the one or more buttons are actuated in a predeterminedmanner and determine the physical possession of the IoT device based onthe determination that the one or more buttons are actuated in thepredetermined manner.

In some embodiments, the IoT device further includes a locationdetection device configured to determine location information associatedwith the IoT device. The physical possession determining system isconfigured to determine location information associated with a userassociated with the IoT device, compare the location informationassociated with the IoT device and the location information associatedwith the user, and determine the physical possession of the IoT devicein response to the location information associated with the IoT devicematching the location information associated with the user.

In some embodiments, the physical possession determining system isconfigured to determine that a power supply associated with the IoTdevice turned off and on in a predetermined manner and determine thephysical possession of the IoT device in response to the determinationthat the power supply associated with the IoT device turned off and onin the predetermined manner.

In some embodiments, the physical possession determining system isconfigured to receive a request for identifying the IoT device andactivate at least one of a light source of the IoT device, a speaker ofthe IoT device, a near-field communication (NFC) transceiver of the IoTdevice, or a radio frequency (RF) transceiver of the IoT device.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 illustrates a block diagram of a multimedia environment,according to some embodiments.

FIG. 2 illustrates a block diagram of a streaming media device,according to some embodiments.

FIG. 3 illustrates a block diagram of an IoT environment, according tosome embodiments.

FIG. 4 illustrates a block diagram of an example IoT device 301,according to some embodiments.

FIGS. 5A-5I illustrate exemplary block diagrams of possessiondetermination system, according to some embodiments

FIG. 6 illustrates an example method for determining physical possessionof a plurality of IoT devices, according to some embodiments.

FIG. 7 illustrates an example computer system useful for implementingvarious embodiments.

In the drawings, like reference numbers generally indicate identical orsimilar elements. Additionally, generally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

DETAILED DESCRIPTION

Provided herein are system, apparatus, device, method and/or computerprogram product embodiments, and/or combinations and sub-combinationsthereof, for determining and/or proving physical possession of one ormore IoT devices.

Various embodiments of this disclosure may be implemented using and/ormay be part of a multimedia environment 102 shown in FIG. 1 . Forexample, multimedia environment 102 can include or support one or moreIoT devices. Multimedia environment 102 can further support provingphysical possession of the one or more IoT devices. It is noted,however, that multimedia environment 102 is provided solely forillustrative purposes, and is not limiting. Embodiments of thisdisclosure may be implemented using and/or may be part of environmentsdifferent from and/or in addition to the multimedia environment 102, aswill be appreciated by persons skilled in the relevant art(s) based onthe teachings contained herein. For example, IoT environment 300 of FIG.3 can implement various embodiments of this disclosure. An example ofthe multimedia environment 102 shall now be described.

Multimedia Environment

FIG. 1 illustrates a block diagram of a multimedia environment 102,according to some embodiments. In a non-limiting example, multimediaenvironment 102 may be directed to streaming media. However, thisdisclosure is applicable to any type of media (instead of or in additionto streaming media), as well as any mechanism, means, protocol, methodand/or process for distributing media.

The multimedia environment 102 may include one or more media systems104. A media system 104 could represent a family room, a kitchen, abackyard, a home theater, a school classroom, a library, a car, a boat,a bus, a plane, a movie theater, a stadium, an auditorium, a park, abar, a restaurant, or any other location or space where it is desired toreceive and play streaming content. User(s) 132 may operate with themedia system 104 to select and consume content.

Each media system 104 may include one or more media devices 106 eachcoupled to one or more display devices 108. It is noted that terms suchas “coupled,” “connected to,” “attached,” “linked,” “combined” andsimilar terms may refer to physical, electrical, magnetic, logical,etc., connections, unless otherwise specified herein.

Media device 106 may be a streaming media device, DVD or BLU-RAY device,audio/video playback device, cable box, and/or digital video recordingdevice, to name just a few examples. Display device 108 may be amonitor, television (TV), computer, smart phone, tablet, wearable (suchas a watch or glasses), appliance, Internet-of-Things (IoT) device,and/or projector, to name just a few examples. In some embodiments,media device 106 can be a part of, integrated with, operatively coupledto, and/or connected to its respective display device 108.

Each media device 106 may be configured to communicate with network 118via a communication device 114. The communication device 114 mayinclude, for example, a cable modem or satellite TV transceiver. Themedia device 106 may communicate with the communication device 114 overa link 116, wherein the link 116 may include wireless (for example, awireless local area network (WLAN) such as WiFi) and/or wiredconnections.

In various embodiments, the network 118 can include, without limitation,wired and/or wireless intranet, extranet, Internet, cellular, Bluetooth,infrared, and/or any other short range, long range, local, regional,global communications mechanism, means, approach, protocol and/ornetwork, as well as any combination(s) thereof.

Media system 104 may include a remote control 110. The remote control110 can be any component, part, apparatus and/or method for controllingthe media device 106 and/or display device 108, such as a remotecontrol, a tablet, laptop computer, smartphone, wearable, on-screencontrols, integrated control buttons, audio controls, or any combinationthereof, to name just a few examples. In an embodiment, the remotecontrol 110 wirelessly communicates with the media device 106 and/ordisplay device 108 using cellular, Bluetooth, infrared, etc., or anycombination thereof. The remote control 110 may include a microphone112, which is further described below.

The multimedia environment 102 may include a plurality of contentservers 120 (also called content providers or sources 120). Althoughonly one content server 120 is shown in FIG. 1 , in practice themultimedia environment 102 may include any number of content servers120. Each content server 120 may be configured to communicate withnetwork 118.

Each content server 120 may store content 122 and metadata 124. Content122 may include any combination of music, videos, movies, TV programs,multimedia, images, still pictures, text, graphics, gaming applications,advertisements, programming content, public service content, governmentcontent, local community content, software, and/or any other content ordata objects in electronic form.

In some embodiments, metadata 124 includes data about content 122. Forexample, metadata 124 may include associated or ancillary informationindicating or related to writer, director, producer, composer, artist,actor, summary, chapters, production, history, year, trailers, alternateversions, related content, applications, and/or any other informationpertaining or relating to the content 122. Metadata 124 may also oralternatively include links to any such information pertaining orrelating to the content 122. Metadata 124 may also or alternativelyinclude one or more indexes of content 122, such as but not limited to atrick mode index.

The multimedia environment 102 may include one or more system servers126. The system servers 126 may operate to support the media devices 106from the cloud. It is noted that the structural and functional aspectsof the system servers 126 may wholly or partially exist in the same ordifferent ones of the system servers 126.

The media devices 106 may exist in thousands or millions of mediasystems 104. Accordingly, the media devices 106 may lend themselves tocrowdsourcing embodiments and, thus, the system servers 126 may includeone or more crowdsource servers 128.

For example, using information received from the media devices 106 inthe thousands and millions of media systems 104, the crowdsourceserver(s) 128 may identify similarities and overlaps between closedcaptioning requests issued by different users 132 watching a particularmovie. Based on such information, the crowdsource server(s) 128 maydetermine that turning closed captioning on may enhance users’ viewingexperience at particular portions of the movie (for example, when thesoundtrack of the movie is difficult to hear), and turning closedcaptioning off may enhance users’ viewing experience at other portionsof the movie (for example, when displaying closed captioning obstructscritical visual aspects of the movie). Accordingly, the crowdsourceserver(s) 128 may operate to cause closed captioning to be automaticallyturned on and/or off during future streamings of the movie.

The system servers 126 may also include an audio command processingmodule 130. As noted above, the remote control 110 may include amicrophone 112. The microphone 112 may receive audio data from users 132(as well as other sources, such as the display device 108). In someembodiments, the media device 106 may be audio responsive, and the audiodata may represent verbal commands from the user 132 to control themedia device 106 as well as other components in the media system 104,such as the display device 108.

In some embodiments, the audio data received by the microphone 112 inthe remote control 110 is transferred to the media device 106, which isthen forwarded to the audio command processing module 130 in the systemservers 126. The audio command processing module 130 may operate toprocess and analyze the received audio data to recognize the user 132’sverbal command. The audio command processing module 130 may then forwardthe verbal command back to the media device 106 for processing.

In some embodiments, the audio data may be alternatively or additionallyprocessed and analyzed by an audio command processing module 216 in themedia device 106 (see FIG. 2 ). The media device 106 and the systemservers 126 may then cooperate to pick one of the verbal commands toprocess (either the verbal command recognized by the audio commandprocessing module 130 in the system servers 126, or the verbal commandrecognized by the audio command processing module 216 in the mediadevice 106).

FIG. 2 illustrates a block diagram of an example media device 106,according to some embodiments. Media device 106 may include a streamingmodule 202, processing module 204, storage/buffers 208, and userinterface module 206. As described above, the user interface module 206may include the audio command processing module 216.

The media device 108 may also include one or more audio decoders 212 andone or more video decoders 214.

Each audio decoder 212 may be configured to decode audio of one or moreaudio formats, such as but not limited to AAC, HE-AAC, AC3 (DolbyDigital), EAC3 (Dolby Digital Plus), WMA, WAV, PCM, MP3, OGG GSM, FLAC,AU, AIFF, and/or VOX, to name just some examples.

Similarly, each video decoder 214 may be configured to decode video ofone or more video formats, such as but not limited to MP4 (mp4, m4a,m4v, f4v, f4a, m4b, m4r, f4b, mov), 3GP (3gp, 3gp2, 3g2, 3gpp, 3gpp2),OGG (ogg, oga, ogv, ogx), WMV (wmv, wma, asf), WEBM, FLV, AVI,QuickTime, HDV, MXF (OP1a, OP-Atom), MPEG-TS, MPEG-2 PS, MPEG-2 TS, WAV,Broadcast WAV, LXF, GXF, and/or VOB, to name just some examples. Eachvideo decoder 214 may include one or more video codecs, such as but notlimited to H.263, H.264, HEV, MPEG1, MPEG2, MPEG-TS, MPEG-4, Theora,3GP, DV, DVCPRO, DVCPRO, DVCProHD, IMX, XDCAM HD, XDCAM HD422, and/orXDCAM EX, to name just some examples.

Now referring to both FIGS. 1 and 2 , in some embodiments, the user 132may interact with the media device 106 via, for example, the remotecontrol 110. For example, the user 132 may use the remote control 110 tointeract with the user interface module 206 of the media device 106 toselect content, such as a movie, TV show, music, book, application,game, etc. The streaming module 202 of the media device 106 may requestthe selected content from the content server(s) 120 over the network118. The content server(s) 120 may transmit the requested content to thestreaming module 202. The media device 106 may transmit the receivedcontent to the display device 108 for playback to the user 132.

In streaming embodiments, the streaming module 202 may transmit thecontent to the display device 108 in real time or near real time as itreceives such content from the content server(s) 120. In non-streamingembodiments, the media device 106 may store the content received fromcontent server(s) 120 in storage/buffers 208 for later playback ondisplay device 108.

Exemplary IoT Environment

FIG. 3 illustrates a block diagram of an IoT environment 300, accordingto some embodiments. According to some embodiments, IoT environment 300can be implemented with multimedia environment 102 of FIG. 1 . Forexample, multimedia environment 102 of FIG. 1 can be part of IoTenvironment 300 or vice versa.

According to some embodiments, IoT environment 300 can include aplurality of IoT devices 301 a-301 n, network 303, one or more systemservers 305, and user device 307. According to some embodiments, IoTdevices 301 a-301 n can be connected to, and communicate with, eachother using a mesh network. In this example, when an IoT device leavesthe plurality of IoT devices 301 a-301 n and/or an IoT device is addedto the plurality of IoT devices 301 a-301 n, the mesh network can beupdated accordingly. In one example, network 303 can be the mesh networkconnecting the plurality of IoT devices 301 a-301 n.

The mesh network can be part of network 303. For example, IoT devices301 a-301 n (collectively referred to as IoT devices 301) can beconnected to each other (e.g., communicate with each other) using themesh network. The mesh network can be implemented using a wireless localarea network (WLAN) such as WiFi. However, the embodiments of thisdisclosure are not limited to this example, and the mesh network can beimplemented using other types of wireless and/or wired networks. In someexamples, network 303 can include the mesh network and another wirelessand/or wired networks. In various embodiments, network 303 can include,without limitation, mesh, wired and/or wireless intranet, extranet,Internet, cellular, Bluetooth, infrared, and/or any other short range,long range, local, regional, global communications mechanism, means,approach, protocol and/or network, as well as any combination(s)thereof.

According to some embodiments, IoT environment 300 can include one ormore system servers 305. System servers 305 may operate to support IoTdevices 301. In some examples, system servers 305 may operate to supportIoT devices 301 from a cloud. It is noted that the structural andfunctional aspects of system servers 305 may wholly or partially existin the same or different systems. According to some embodiments, IoTdevices 301 can communicate with system servers 305 through network 303.In some examples, system servers 305 can be associated with systemservers 126 of FIG. 1 . For example, the structural and functionalaspects of system servers 305 may wholly or partially exist in the sameor different ones of the system servers 126.

According to some embodiments, system servers 305 can include one ormore user accounts associated with IoT devices 301 and/or theirassociated network 303. In a non-limiting example, IoT devices 301 caninclude IoT devices associated with a physical property of user 332 onone network 303. In this example, IoT devices 301 and network 303 can beassociated with the user account of user 332. In another non-limitingexample, user 332 can have two physical properties where each physicalproperty has its associated IoT devices and network. In this example,the IoT devices and networks are associated with the user account ofuser 332. However, the user account can include information indicatingwhich IoT devices and which networks are associated with which of thetwo user properties.

IoT environment 300 can also include one or more user devices 307.According to some embodiments, user device 307 can be any of a personaldigital assistant (PDA), desktop workstation, laptop or notebookcomputer, netbook, tablet, smart phone, smart watch or other wearableappliance, to name a few non-limiting examples, or any combinationthereof. In some examples, a user (e.g., user 332) can prove physicalpossession of one or more of IoT devices 301 using user device 307.Additionally, or alternatively, user 332 can control and/or configureone or more IoT devices 301 using user device 307. For example, IoTdevice 301 can use radio frequency (RF) signals (e.g., using WLAN) toreceive configuration and/or control information from user device 307.

Various embodiments of this disclosure are directed to proving physicalpossession (and therefore ownership) of IoT device 301 so user device307 can configure and/or control IoT device 301. Additionally, oralternatively, some embodiments of this disclosure are directed tosecurely adding IoT devices without needing to manually set up each oneof the IoT devices. Also, some embodiments of this disclosure aredirected to securely transferring ownership of IoT devices to anotheruser and/or user account. Also, some embodiments of this disclosure aredirected to determining/proving possession of a subset of a plurality ofIoT devices to determine/prove possession of the plurality of IoTdevices.

IoT devices 301 can include any IoT device. As some non-limitingexamples, IoT devices 301 can include smart appliances such as, but nolimited to, smart TVs, smart refrigerators, smart washers, smart dryers,smart dishwashers, smart ovens and gas tops, smart microwaves, smartheating, ventilation, and air conditionings (HVACs), smart fans, smartblinds, or the like. As other non-limiting examples, IoT devices 301 caninclude smart home security systems, smart locks, smart firealarms/systems, or the like. IoT devices 301 can include sensors used inhomes, offices, factories, medical sensors, fitness sensors/trackers, orthe like. It is noted that although some embodiments of this disclosureare discussed with respect to some exemplary IoT devices, theembodiments of this disclosure are not limited to these examples and canbe applied to other IoT devices.

According to some embodiments, IoT environment 300 can be used fordetermining and/or proving physical possession of one or more IoTdevices 301. According to some embodiments, by proving physicalpossession of, for example, IoT device 301 a, a user can establishownership of IoT device 301 n as well as IoT device 301 a, and/or therest of IoT devices 301. In other words, an owner of IoT device 301 canbe the user who has the physical possession of IoT device 301, accordingto some embodiments. As the owner of IoT device 301, the user canconfigure and control IoT device 301, in some embodiments. Additionally,or alternatively, as the owner of IoT device 301, the user can controlwho else can access IoT device 301. As discussed in more detail below, auser (e.g., user 332) can use user device 307 with IoT device 301(and/or system servers 305) to prove physical possession of IoT device301, according to some embodiments. Additionally, or alternatively, theuser (e.g., user 332) can operate on IoT device 301 to prove physicalpossession of IoT device 301.

There may be different states or levels of physical possession. Eachstarting state may have different requirements for proving physicalpossession. Some non-limiting examples of starting physical possessionstates and implications about that starting states are discussed below.

An exemplary starting physical possession state on an IoT device 301 canbe a factory default state. This state can imply that the first user whotries to possess IoT device 301 may need less security than otherwiseneeded. In this example, using a Quick Response (QR) code (as anon-limiting example) can be enough for proving physical possession ofIoT device 301.

Another exemplary starting physical possession state can be previouslypossessed by a first owner but the first owner gave up possession of IoTdevice 301. In this example, similar to factory default state example,lower threshold for proving physical possession of IoT device 301 can beused. For example, if the first owner sells IoT device 301 to a seconduser, the second user can prove ownership and physical possession withlower threshold of requirements.

Another exemplary starting physical possession state can be currentlypossessed and recently used. In this example, a higher (e.g., a highest)level of proving possession can be used as this state can be one of themost likely states to be hacked. According to some embodiments, acombination of physical possession proofs and/or high (e.g., highest)security possession proofs can be used.

Another exemplary starting physical possession state can be currentlypossessed but not accessed in a long time (e.g., a period of time morethan a threshold time). In this example, a lower level of provingpossession can be used. A non-limiting example of this state can includeIoT device 301 in a house, where the house is sold to a new ownerwithout active transfer of IoT device 301.

Another exemplary starting physical possession state can be a statewhere IoT device 301 has just been installed by an installer, and isawaiting an owner to possess IoT device 301, but the possession has notbeen actively transferred by the installer. This state can also use alower (or a medium) level of proving possession.

Another exemplary starting physical possession state can be a statewhere IoT device 301 has just been installed by an installer, and theinstaller transferred possession of IoT device 301 to a new owner viaactive means. In a non-limiting example, an email can be used to provephysical possession by the new owner.

Another exemplary starting physical possession state can be a statewhere IoT device 301 is possessed by an owner but is marked as a rentaldevice. In a non-limiting example, IoT device 301 can be in a house thatis owned by the owner and is rented to a renter. In this exemplarystarting state, lower requirements for physical possession by the rentercan be used. However, the requirements can also allow the owner toremove possession of the renter, according to some embodiments. In someexamples, the ownership can be transferred using, for example, an email.Additionally, or alternatively, other mechanisms can be used fortransferring ownership. In some examples, the requirements fortransferring ownershipcan also include mechanisms for transferringownershipbetween renters without the owner’s assistance. In anon-limiting example, the owner can set a possession timer length (forexample, but not limited to, 1 day, 7 days, 30 days, etc.) for IoTdevice 301. Therefore, if a first renter has not accessed IoT device 301for the possession timer length, the ownership can be transferred to theowner and/or to a second renter. In some examples, a higher level ofproving possession can be used for transferring ownership to the secondrenter. Additionally, or alternatively, the requirement may not allow aprevious owner to be deleted.

Another exemplary starting physical possession state can be a statewhere IoT device 301 is possessed by an owner and is marked as ashort-time rental (e.g., a hotel and/or a special case of rentaldiscussed above). In some examples, the ability for a user to physicallypossess IoT device 301 to take it over can be disabled. In anon-limiting example, a user in the hotel will not be able to take overIoT device 301 even though the user has physical possession.

Another exemplary starting physical possession state can be transfer ofownership from one owner to a new owner using active means. In anon-limiting example, receiving a transfer email can be used to transferphysical possession. In a non-limiting example, if the new owner doesnot claim the transfer, the old owner can take back the possession.

Another exemplary starting physical possession state can be forcedtransfer of possession from server side (e.g., system servers 305). Inthis example, system servers 305 can use mechanisms to over-ridepossession of IoT device 301.

According to some embodiments, if a user sets IoT device 301 (e.g.,using user device 307) into a mode that allows taking possession, butthen the user does not take possession, IoT device 301 can timeout(after a threshold period of time) and go back into the previouspossession mode IoT device 301 was in.

FIG. 4 illustrates a block diagram of an example IoT device 301,according to some embodiments. IoT device 301 may include one or moresensors 402, processing module 404, one or more actuators 406,storage/buffers 408, power switch 410, transceiver 412, and physicalpossession determination system 414, according to some embodiments.Although not shown, IoT device 301 can also include a user interfacemodule for interfacing with a user (e.g., user 332 of FIG. 3 ). It isnoted that IoT device 301 can include more or fewer systems. Also, thestructural and functional aspects of the systems in IoT device 301 maywholly or partially exist in the same or different ones of these system.

According to some embodiments, sensor 402 of IoT device 301 can beconfigured to measure one or more parameters in IoT environment 300 ofFIG. 3 . Depending on the structural and functional aspects of IoTdevice 301, IoT device 301 can include one or more sensors 402.Similarly, depending on the structural and functional aspects of IoTdevice 301, IoT device 301 can include one or more actuators to performone or more operations within IoT environment 300 of FIG. 3 . In someembodiments, the operations performed by actuator 406 can be based onthe parameter(s) measured by sensor 402.

According to some embodiments, processing module 404 can be configuredto control operations of sensor 402 and actuator 406. Additionally, oralternatively, processing module 404 can be configured to control thecommunication between IoT device 301 with system servers 305 and/or userdevice 307. Processing module 404 can also be configured to receivecontrol and configuration information for IoT device 301 and implementthese control and configuration information.

In some examples, control information, configuration information,physical possession information, and/or ownership information can bestored in storage/buffers 408. For example, storage/buffers 408 canstore information associated with a user account associated with theuser and/or the owner of IoT device 301. Additionally, or alternatively,storage/buffers 408 can store information associated with network 303.Information associated with network 303 can include, but are not limitedto, identifier of network 303, password for network 303, identifiers ofdevices coupled to network 303, or the like. Storage/buffers 408 canstore other information, data, and/or instructions used for operatingIoT device 301

According to some embodiments, processing module 404 operates withphysical possession determination system 414 to determine physicalpossession and/or ownership of IoT device 301. As discussed in moredetail below, physical possession determination system 414 can beconfigured to interact with a user (e.g., user 332 of FIG. 3 ) and/oruser device 307 to determine physical possession and/or ownership of IoTdevice 301. In some examples, physical possession determination system414 can be part of processing module 404. Additionally, oralternatively, physical possession determination system 414 can includeone or more processors to implement functions and structures of physicalpossession determination system 414.

IoT device 301 can include one or more transceivers 412. Transceiver 412can include processors, controllers, radios, sockets, plugs, buffers,and like circuits/devices used for connecting to and communicating onnetworks. In some examples, transceivers 412 can include one or more ofa cellular subsystem, a WLAN subsystem, a Bluetooth™ subsystem, anear-field communication (NFC), or the like. Transceivers 412 caninclude one or more circuits to enable connection(s) and communicationbased on, for example, Bluetooth™ protocol (or similar protocols).Additionally, or alternatively, transceiver 412 can include one or morecircuits to enable connection(s) and communication over WLAN networkssuch as, but not limited to, networks based on standards described inIEEE 802.11. For example, transceivers 412 can include one or morecircuits to enable communication over mesh networks. Transceiver 412enables IoT device 301 to communicate with other IoT devices, withsystem servers 305, and/or user device 307. For example, transceiver 412enables IoT device 301 to communicate with other IoT devices, withsystem servers 305, and/or user device 307 using network 303 of FIG. 3 .

IoT device 301 can include power switch 410 for turning on and off IoTdevice 301. According to some embodiments, one embodiment to provephysical possession of IoT device 301 can include turning off and on thepower to IoT device 301 multiple times. For example, a user (e.g., user332 of FIG. 3 ) can use power switch 410 of IoT device 301 to turn offand on the power to IoT device 301 multiple times. Additionally, oralternatively, the user can use other embodiments to turn off and on apower supply to IoT device 301 multiple times. According to someembodiments, physical possession determination system 414 can track thenumber of off/on cycles and/or a duration for each off/on cycle.Physical possession determination system 414 can compare the number ofoff/on cycles and/or the duration for each off/on cycle with respectiveconditions. If physical possession determination system 414 determinesthat the one or more of the conditions are satisfied, physicalpossession determination system 414 can determine that a user hasphysical possession of IoT device 301. Additionally, or alternatively,physical possession determination system 414 can enter IoT device 301 into a pairing mode in response to the one or more of the conditions beingsatisfied.

In a non-limiting example, physical possession determination system 414can compare the duration of the off/on cycles with a first threshold. Ifthe duration is less than the threshold, physical possessiondetermination system 414 can determine that a user is trying toestablish physical possession. Additionally, or alternatively, physicalpossession determination system 414 can compare the number of off/oncycles with a second threshold. In a non-limiting example, the secondthreshold can be three. However, the embodiments of this disclosure caninclude any number. If the number of off/on cycles is equal to or morethan the second threshold, physical possession determination system 414can determine that the user has physical possession of IoT device 301.In this example, physical possession determination system 414 candetermine that the user has physical possession of IoT device 301.Additionally, or alternatively, physical possession determination system414 can enter IoT device 301 into a pairing mode such that IoT device301 can pair with, for example, user device 307 of the user.

In one example, if physical possession determination system 414 entersIoT device 301 into the pairing mode but no pairing occurs, physicalpossession determination system 414 can stop the pairing mode after aspecific time period and return IoT device 301 in a previously pairedmode.

In some examples, IoT device 301 can use different pairing modes. Eachpairing mode can be associated with a threshold of number of off/oncycles. Physical possession determination system 414 can determine aspecific pairing mode based on the number of off/on cycles that physicalpossession determination system 414 counts and the respective threshold.

According to some embodiments, an example embodiment to prove physicalpossession of IoT device 301 can include turning off and on IoT device301 once, along with communication through user device 307. In anon-limiting example, IoT device 301 can establish connection andcommunication with user device 307 through, for example, transceiver412. In some examples, the connection can be based on a Bluetooth™connection. Additionally, or alternatively, the connection can be basedon a WLAN connection. To determine physical possession of IoT device301, physical possession determination system 414 can send a message touser device 307 for the user of user device 307 to turn off and on thepower to IoT device 301 once (or multiple times). After sending themessage, physical possession determination system 414 can determinewhether IoT device 301 is turned off and on in response to, and basedon, the message sent to user device 307. If physical possessiondetermination system 414 determines that the instructions in the messagewere satisfied, physical possession determination system 414 candetermine that the user of user device 307 has physical possession ofIoT device 301.

According to some embodiments, in addition to, or in alternative to,using power switch 410 to turn off and on the power to IoT device 301, asmart switch and/or a smart outlet can be used to turn off and on thepower to IoT device 301 to prove physical possession of IoT device 301.For example, IoT device 301 can be coupled to a smart switch and/or asmart outlet (not shown) that can control the power to IoT device 301.In this example, IoT device 301 can be downstream of the smart switchand/or the smart outlet. In some examples, possession determinationsystem 414 of IoT device 301 can determine the number and/or duration ofoff/on cycles created by the smart switch and/or smart outlet todetermine physical possession of IoT device 301. In some examples,possession determination system 414 can determine physical possession ofIoT device 301 by determining that the instructions in the message touser device 307 were satisfied when the power to IoT device 301 isturned off and on using the smart switch and/or the smart outlet.

In another exemplary embodiment, a downstream device can request anupstream device to control the power to the downstream device. In thisexample, the physical possession of the upstream device can bedetermined. For example, IoT device 301 is coupled to another IoT device(e.g., a smart switch, a smart outlet, or other IoT devices) such thatIoT device 301 is downstream of the other IoT device, and the other IoTdevice can control the power to IoT device 301. In this example, theobject is to determine the physical possession of the other IoT device(the upstream IoT device). In this example, IoT device 301 and the otherIoT device can communicate with each other. For example, both are on thesame mesh network (e.g., can communicate through a WLAN). IoT device 301can send a message to other IoT device to turn off and on the power toIoT device 301 once or multiple times. Possession determination system414 can determine if the other IoT device follows the instructions inthe message. If the other IoT device follows the instructions,possession determination system 414 can determine the physicalpossession of the other IoT device. For example, possessiondetermination system 414 can determine the other IoT device and IoTdevice 301 are physically possessed by the same user.

In another exemplary embodiment, an upstream IoT device can determinephysical possession of a downstream IoT device. For example, theupstream IoT device (e.g., a smart switch) that provides power to thedownstream IoT device (e.g., a smart bub) can detect the current beingused the downstream IoT device. By detecting the current, the upstreamIoT device can detect the downstream IoT device, determine that the IoTdownstream device is part of the IoT network, and/or determine thephysical possession of the downstream IoT device. For example, theupstream IoT device can determine that the downstream IoT device has thesame physical possession as the upstream IoT device. In another example,the upstream IoT device (e.g., a smart switch) that provides power tothe downstream IoT device (e.g., a smart bub) can detect a correlationbetween removing power to the downstream IoT device and the downstreamIoT device being off the IoT network. By detecting the correlation, theupstream IoT device can detect the downstream IoT device, determine thatthe IoT downstream device is part of the IoT network, and/or determinethe physical possession of the downstream IoT device. For example, theupstream IoT device can determine that the downstream IoT device has thesame physical possession as the upstream IoT device. In some examples,the above embodiments can be used for automatic addition and/orreplacement of downstream IoT devices in the IoT network.

According to some embodiments, turning off and on IoT device 301 can bebased on predetermined information (e.g., predetermined approach(es))that is shared between IoT device 301 and user device 307. In someexamples, the predetermined information can be shared between IoT device301 and user device 307 by system server 305. System server 305 canstore and manage the user account associated with IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more magnetic detectors. FIG.5A illustrates a block diagram of possession determination system 414having one or more magnetic detectors 502, according to someembodiments. Possession determination system 414 can include one or moremagnetic detectors 502 configured to detect the presence of a magnet. Ina non-limiting example, magnet detector 502 can include a magnetometerthat can measure, for example, strength and/or direction of a magneticfield. However, magnetic detector 502 can include any other sensorsconfigured to detect the presence of a magnet and/or measure itsmagnetic field. In some examples, magnetic detector 502 can generate asignal based on the detection of the presence of the magnet. Possessiondetermination system 414 can measure the generated signal and determinethe physical possession of IoT device 301. For example, a user of IoTdevice 301 can hold a magnet close to IoT device 301. Magnetic detector502 can generate a signal (e.g., an electric signal) based on detectingthe presence of the magnet. If a parameter of the generated signal meetsa condition (e.g., a power of the signal is greater than a threshold),possession determination system 414 can determine that the user hasphysical possession of IoT device 301.

In some examples, the user brings the magnet in close proximity of IoTdevice 301 during (or after) the boot operation of IoT device 301.Additionally, or alternatively, the user can bring the magnet in closeproximity of IoT device 301 at any time during the operation of IoTdevice 301. In some examples, IoT device 301 (e.g., using possessiondetermination system 414) can send a message to the user (e.g., throughuser device 307) to prompt the user to bring the magnet in closeproximity of IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more RF transceivers. FIG. 5Billustrates a block diagram of possession determination system 414having one or more transceivers 504, according to some embodiments.Although transceiver 504 is illustrated in FIG. 5B as part of possessiondetermination system 414, transceiver 504 can be (or be part of)transceiver 412 of FIG. 4 . According to some embodiments, transceiver504 can be one or more of a WLAN subsystem, a Bluetooth™ subsystem, orthe like. For example, possession determination system 414 (and/or IoTdevice 301) can communicate with user device 307 using WLAN (e.g., WiFi)and/or Bluetooth™. In some examples, transceiver 504 can be configuredto operate using low power RF signals. In this case, user device 307 canbe close to IoT device 301 to be able to correctly receive and decodethe signals from possession determination system 414 (and/or IoT device301).

In a non-limiting example, possession determination system 414 cantransmit one or more packets (e.g., RF packets) to user device 307using, for example, transceiver 504. The one or more packets can bepredetermined packets used by possession determination system 414 todetermine the physical possession of IoT device 301. In someembodiments, after receiving the packets, user device 307 can send oneor more response packets (e.g., RF packets) back to IoT device 301.After receiving the response packets, possession determination system414 can determine whether the user of user device 307 has physicalpossession of IoT device 301 based on the transmitted and/or receivedpackets. In a non-limiting example, possession determination system 414can compare the received packets with the predetermined packet todetermine whether the user of user device 307 has physical possession ofIoT device 301. The predetermined packets can be stored instorage/buffers 408.

Additionally, or alternatively, after receiving the packets from IoTdevice 301, user device 307 can communicate the received packets (or asubset of the packets or one or more response packets) with systemservers 305. System servers 305 can communicate with possessiondetermination system 414 of IoT device 301 to confirm the physicalpossession of IoT device 301 by the user of user device 307.

In a non-limiting example, user device 307 can be or can include adongle. For example, user device 307 can be an RF transceiver dongle(for example, but not limited to, a WLAN dongle, a Bluetooth™ dongle, orthe like) that can communicate with IoT device 301 for determiningphysical possession of IoT device 301.

According to some embodiments, predetermined packet(s) can be based onpredetermined information that is shared between IoT device 301 and userdevice 307. In some examples, the predetermined information can beshared between IoT device 301 and user device 307 by system server 305.System server 305 can store and manage the user account associated withIoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more QR codes or otherprinted secrets on IoT device 301. In this example, IoT device 301 caninclude one or more QR codes that can be physically located on IoTdevice 301. Although some examples are discussed with respect to QRcodes, the embodiments of this disclosure are not limited to theseexamples, and instead other device-specific secrets/codes can be used.In a non-limiting example, to determine physical possession of IoTdevice 301, a user can use user device 307 to scan the QR code of theIoT device 301. After scanning the QR code, user device 307 candetermine identifying information associated with IoT device 301 and adevice-specific secret associated with IoT device 301, according to someembodiments.

User device 307 can communicate one or more of the identifyinginformation and the device-specific secret associated with IoT device301 to, for example, IoT device 301 and/or system servers 305 to provethe user’s physical possession of IoT device 301. In one example, systemservers 305 can determine the user’s physical possession of IoT device301 based on the received information from user device 307. Systemservers 305 can communicate the determination of the user’s physicalpossession of IoT device 301 to, for example, possession determinationsystem 414 of IoT device 301. In another example, user device 307 candirectly communicate with IoT device 301 (e.g., through network 303) toprove physical possession of IoT device 301.

According to some embodiments, predetermined code can be based onpredetermined information that is shared between IoT device 301 and userdevice 307. In some examples, the predetermined information can beshared between IoT device 301 and user device 307 by system server 305.System server 305 can store and manage the user account associated withIoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more buttons or switches onIoT device 301. FIG. 5C illustrates a block diagram of possessiondetermination system 414 having one or more buttons 506, according tosome embodiments. Buttons 506 can include, but are not limited to,switches, capacitive touch switches, capacitive touch buttons, or thelike. However, the embodiments of this disclosure are not related tothese examples, and buttons 506 can include other sensors. For example,buttons 506 can include other sensors (e.g., touch sensors) to measure,for example, the presence of a user’s touch.

In a non-limiting example, IoT device 301 (e.g., using possessiondetermination system 414) and/or system servers 305 can request the userto actuate one or more buttons 506. In one example, IoT device 301 caninclude a user interface for requesting the user to actuate one or morebuttons 506. In this example, the request can be displayed on the userinterface, can be sent using a sound system, or the like. Additionally,or alternatively, IoT device 301 (e.g., using possession determinationsystem 414) and/or system servers 305 can send the request to userdevice 307. IoT device 301 can send the request to user device 307directly (e.g., through network 303) and/or through system servers 305.In response to the request, the user can actuate one or more buttons506. If possession determination system 414 determines that one or morebuttons 506 are actuated in response to the request that was sent to theuser, possession determination system 414 can determine that the userhas physical possession of IoT device 301.

According to some embodiments, the process of actuating one or morebuttons 506 can include actuating a single button once. Additionally, oralternatively, different approaches of actuating buttons 506 can be usedfor determining physical possession. In a non-limiting example, the useris to actuate (e.g., press) a single button for at least a predeterminedperiod of time to determine physical possession. In another non-limitingexample, the user is to actuate (e.g., press) a single button at least apredetermined number of times to determine physical possession. Inanother non-limiting example, the user is to actuate (e.g., press)multiple buttons in a predetermined manner, for at least a predeterminedperiod of time, and/or at least a predetermined number of times todetermine physical possession. Depending on the scheme used, possessiondetermination system 414 can determine if the user has successfully metthe condition(s) of the scheme and determine if the user has physicalpossession of IoT device 301.

According to some embodiments, predetermined approaches for actuatingthe button(s) can be based on predetermined information that is sharedbetween IoT device 301 and user device 307. In some examples, thepredetermined information can be shared between IoT device 301 and userdevice 307 by system server 305. System server 305 can store and managethe user account associated with IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more accelerometers in IoTdevice 301. FIG. 5D illustrates a block diagram of possessiondetermination system 414 having accelerometer 508, according to someembodiments. Accelerometer 508 can be configured to measure accelerationforces to IoT device 301. According to some embodiments, possessiondetermination system 414 can determine a users’ physical possessionbased on acceleration force applied by the user to IoT device 301. In anon-limiting example, the acceleration force can be applied during theboot operation of IoT device 301. In another non-limiting example, theacceleration force can be applied during normal operation of IoT device301.

In some examples, the acceleration force can be applied without IoTdevice 301 prompting the user to apply the force. Additionally, oralternatively, IoT device 301 (and/or system servers 305) can prompt theuser to apply the acceleration force. In a non-limiting example, IoTdevice 301 (e.g., using possession determination system 414) and/orsystem servers 305 can request the user to apply the acceleration force.In one example, IoT device 301 can include a user interface forrequesting the user to apply the acceleration force. In this example,the request can be displayed on the user interface, can be sent using asound system, or the like. Additionally, or alternatively, IoT device301 (e.g., using possession determination system 414) can send therequest to user device 307. IoT device 301 can send the request to userdevice 307 directly (e.g., through network 303) and/or through systemservers 305. In response to the request, the user can apply theacceleration force.

If possession determination system 414 senses (e.g., measures) theacceleration force using accelerator 508, possession determinationsystem 414 can determine that the user has physical possession of IoTdevice 301. In some examples, the acceleration force is in response to arequest from IoT device 301 (and/or system servers 305). In someexamples, the acceleration force is applied without any request form IoTdevice 301 (and/or system servers 305).

According to some embodiments, using the accelerometer can be based onpredetermined information that is shared between IoT device 301 and userdevice 307. In some examples, the predetermined information can beshared between IoT device 301 and user device 307 by system server 305.System server 305 can store and manage the user account associated withIoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more near-field communication(NFC) transceivers and/or one or more NFC tags in IoT device 301. FIG.5E illustrates a block diagram of possession determination system 414having NFC transceiver 510 and NFC tag 512, according to someembodiments. Although NFC transceiver 510 is illustrated withinpossession determination system 414 in FIG. 5E, NFC transceiver 510 canbe (or be part of) transceiver 412 of FIG. 4 . According to someembodiments, NFC transceiver 510 can be a transceiver configured tooperate based on NFC communication protocols.

According to some embodiments, NFC tag 512 can include digitizedinformation configured to be read by an NFC reader. NFC tag 512 caninclude the digitized information embedded in a tag that can be poweredusing inductive coupling. A user can use user device 307, which can beor can include an NFC reader, with NFC tag 512 to prove the user’sphysical possession of IoT device 301. In a non-limiting, to determinephysical possession of IoT device 301, a user can use user device 307 toscan or read the NFC tag 512. After scanning NFC tag 512, user device307 can determine identifying information associated with IoT device 301and a device-specific secret associated with IoT device 301, accordingto some embodiments.

User device 307 can communicate one or more of the identifyinginformation and the device-specific secret associated with IoT device301 to, for example, IoT device 301 and/or system servers 305 to provethe user’s physical possession of IoT device 301. In one example, systemservers 305 can determine the user’s physical possession of IoT device301 based on the received information from user device 307. Systemservers 305 can communicate the determination of the user’s physicalpossession of IoT device 301 to, for example, possession determinationsystem 414 of IoT device 301. In another example, user device 307 candirectly communicate with IoT device 301 (e.g., through network 303) toprove physical possession of IoT device 301.

In addition to, or alternative to, NFC tag 512, possession determinationsystem 414 can include NFC transceiver 510 for communicating with userdevice 307. In one example, a two-way communication between NFCtransceiver 510 and user device 307 can be established to determine thephysical possession of IoT device 301 by the user of user device 307.The two-way communication can include an NFC peer-to-peer communicationfor exchanging information in, for example, an ad hoc manner. In anon-limiting example, NFC transceiver 510 can send a first message(e.g., one or more NFC packets) to user device 307. In response, userdevice 307 can send a second message (e.g., one or more NFC packets) toNFC transceiver 510. After examining the second message, possessiondetermination system 414 can determine that the user of user device 307has physical possession of IoT device 301. In a non-limiting example,possession determination system 414 can compare the received NFC packetswith one or more predetermined packets (and/or with transmitted NFCpackets) to determine whether the user of user device 307 has physicalpossession of IoT device 301. The predetermined packets can be stored instorage/buffers 408.

Additionally, or alternatively, after receiving the NFC packet from IoTdevice 301, user device 307 can communicate the second message (e.g.,one or more NFC packets) with system servers 305 to provide that theuser of user device 307 has physical possession of IoT device 301.System servers 305 can communicate the determination of physicalpossession to IoT device 301, according to some examples.

According to some embodiments, the NFC packets and/or the NFC tag can bebased on predetermined information that is shared between IoT device 301and user device 307. In some examples, the predetermined information canbe shared between IoT device 301 and user device 307 by system server305. System server 305 can store and manage the user account associatedwith IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more speakers and/or one ormore microphones in IoT device 301. FIG. 5F illustrates a block diagramof possession determination system 414 having speaker 514 and/ormicrophone 516, according to some embodiments. Speaker 514 and/ormicrophone 516 can be (or be part of) sensor 402 of FIG. 4 .

According to some embodiments, user device 307 can send an audio signalto IoT device 301 to prove the user’s physical possession of IoT device301. For example, a predetermined audio signal is used to determinephysical possession by possession determination system 414. User device307 can send the predetermined audio signal to IoT device 301. Userdevice 307 can send the audio signal in response to a request from IoTdevice 301 and/or system servers 305, in some examples. Additionally, oralternatively, user device 307 can send the audio signal without anyrequest from IoT device 301 and/or system servers 305. Microphone 516can receive the audio signal.

In some examples, possession determination system 414 can compare thereceived audio signal with the predetermined audio signal that can bestored in, for example, storage/buffers 408. Additionally, oralternatively, possession determination system 414 can determineinformation associated with the received audio signal, and can comparethe determined information with predetermined information. If thereceived audio signal matches the predetermined audio signal (or thedetermined information matches the predetermined information),possession determination system 414 can determine that the user of userdevice 307 has physical possession of IoT device 301.

According to some embodiments, IoT device 301 can send an audio signalto user device 307 for proving the user’s physical possession of IoTdevice 301. For example, a predetermined audio signal is used todetermine physical possession by possession determination system 414.Speaker 514 with possession determination system 414 can generate andtransmit the predetermined audio signal. User device 307 can receive theaudio signal from IoT device 301. In some examples, speaker 514 can sendthe audio signal in response to a process for determining physicalpossession being initiated. After receiving the audio signal, userdevice 307 can compare the received audio signal with the predeterminedaudio signal stored in, for example, user device 307. Additionally, oralternatively, user device 307 can determine information associated withthe received audio signal, and can compare the determined informationwith predetermined information. If the audio signals match (or thedetermined information matches the predetermined information), userdevice 307 can send a message to IoT device 301 and/or system servers305 to indicate that the audio signals have matched, according to someembodiments. Based on the message, possession determination system 414can determine that the user of user device 307 has physical possessionof IoT device 301.

According to some embodiments, the predetermined information is sharedbetween IoT device 301 and user device 307. In some examples, thepredetermined information can be shared between IoT device 301 and userdevice 307 by system server 305. System server 305 can store and managethe user account associated with IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more light sources and/or oneor more light sensors in IoT device 301. FIG. 5G illustrates a blockdiagram of possession determination system 414 having light source 518and/or light sensor 520, according to some embodiments. Light source 518and/or light sensor 520 can be (or be part of) sensor 402 of FIG. 4 ,according to some embodiments. Light source 518 can include any lightsource such as, but not limited to, infrared (IR) light source, visiblelight source, laser source, or the like. Similarly, light sensor 520 caninclude any sensor or detector configured to detect light such as, butnot limited to, IR light, visible light, laser, or the like.

In a non-limiting example, light sensor 520 can include a visible lightsensor. To determine physical possession of IoT device 301, user device307 can be configured to generate and emit a signal (e.g., visiblelight) toward IoT device 301. Light sensor 520 can detect the signal(e.g., the visible light) form user device 307. Possession determinationsystem 414 can use the detected signal (e.g., the visible light) todetermine physical possession of IoT device 301 by the user of userdevice 307. In a non-limiting example, user device 307 can generate andemit the signal (e.g., the visible light) toward IoT device 301 inresponse to a request from IoT device 301 and/or system servers 305. Inanother non-limiting example, the signal (e.g., the visible light)generated and emitted by user device 307 can be based on predeterminedinformation. After detecting the signal at light sensor 520, possessiondetermination system 414 can compare the information associated with thedetected signal with the predetermined information stored in IoT device301 (e.g., in storage/buffers 408). If the detected information matchwith the predetermined information, possession determination system 414can determine that the user of user device 307 has physical possessionof IoT device 301.

In a non-limiting example, light sensor 520 can include an IR sensor. Todetermine physical possession of IoT device 301, user device 307 can beconfigured to generate and emit a signal (e.g., IR light) toward IoTdevice 301. Light sensor 520 can detect the signal (e.g., the IR light)form user device 307. Possession determination system 414 can use thedetected signal (e.g., the IR light) to determine physical possession ofIoT device 301 by the user of user device 307. In one example, userdevice 307 can generate and emit the signal (e.g., the IR light) towardIoT device 301 in response to a request from IoT device 301 and/orsystem servers 305. In another example, the signal (e.g., the IR light)generated and emitted by user device 307 can be based on predeterminedinformation. After detecting the signal at light sensor 520, possessiondetermination system 414 can compare the information associated with thedetected signal with the predetermined information stored in IoT device301 (e.g., in storage/buffers 408). If the detected information matchwith the predetermined information, possession determination system 414can determine that the user of user device 307 has physical possessionof IoT device 301. In a non-limiting example, user device 307 caninclude a remote control device (e.g., remote control 110 of FIG. 1 )configured to generated the signal (e.g., the IR light) based on thepredetermined information. For example, the remote control device caninclude a button used for proving (and controlling/configuring) IoTdevice 301.

In a non-limiting example, light source 518 can generate and emit asignal (e.g., visible light, IR light, laser, or the like). In oneexample, light source 518 can include a light emitting diode (LED).However, the embodiments of this disclosure can include other lightsources. To determine physical possession of IoT device 301, user device307 can be configured to receive the signal (e.g., capture the visiblelight, the IR light, the laser, or the like). In some examples, thesignal is generated based on predetermined information. Thepredetermined information can include a code associated with IoT device301. In one example, user device 307 can include a light sensor (e.g., acamera, an IR sensor, or the like) to receive and capture the signalfrom IoT device 301. In another example, user device 307 can include adongle connected to user device 307. The dongle can include a lightsensor (e.g., a camera, an IR sensor, or the like) to receive andcapture the signal from IoT device 301. After receiving the signal fromIoT device 301, user device 307 can determine information (e.g., a code)from the received signal. In one example, user device 307 cancommunicate the determined information (e.g., the determined code) backto IoT device 301 directly and/or through system servers 305 to provethat the user of user device 307 has physical possession of IoT device301. Additionally, or alternatively, user device 307 can communicate thedetermined information (e.g., the determined code) to system servers 305to prove that the user of user device 307 has physical possession of IoTdevice 301.

In another non-limiting example, IoT device 301 can use both lightsource 518 and light sensor 520 for proving physical possession of IoTdevice 301. In this example, the user can prove its physical possessionof IoT device 301 by using a reflective device. For example, lightsource 518 can generate and emit a signal (e.g., visible light, IRlight, laser, or the like). The signal can be based on predeterminedinformation (e.g., a predetermined code) associated with IoT device 301.If the user uses the reflective device in the proximity of IoT device301, light sensor 520 can receive and capture the reflected signal(e.g., reflected visible light, reflected IR light, reflected laser, orthe like) reflected from the user’s reflective device. Possessiondetermination system 414 can determine information (e.g., a code) fromthe captured signal and compare the determined information (e.g., thedetermined code) with the stored predetermined information (e.g.,predetermined code stored in, for example, storage/buffers 408). If thedetermined information (e.g., the determined code) and the predeterminedinformation (e.g., predetermined code) match, possession determinationsystem 414 can determine that the user has physical possession of IoTdevice 301.

According to some embodiments, the predetermined information is sharedbetween IoT device 301 and user device 307. In some examples, thepredetermined information can be shared between IoT device 301 and userdevice 307 by system server 305. System server 305 can store and managethe user account associated with IoT device 301.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using the location of IoT device 301. FIG.5H illustrates a block diagram of possession determination system 414having location detection device 522, according to some embodiments.Location detection device 522 can be (or be part of) sensor 402 of FIG.4 , according to some embodiments. Location detection device 522 caninclude global navigation satellite systems (GNSS) device such as aglobal positioning system (GPS). However, the embodiments of thisdisclosure are not limited to these examples and location detectiondevice 522 can include any other systems configured to determine andprovide a location of IoT device 301. In a non-limiting example,location detection device 522 can determine and provide the location ofIoT device 301 with an accuracy of about 1 m, about 1 cm, about 1 mm, orany other accuracy.

In some embodiments, possession determination system 414 can use thedetermined location of IoT device 301 from location detection device 522and location information associated with the user of IoT device 301 todetermine the user’s physical possession of IoT device 301. In anon-limiting example, IoT device 301 is to be used with a physicalproperty associated with the user. Possession determination system 414(alone or with system servers 305) can determine location informationassociated with the user’s property. Possession determination system 414can compare the determined location information associated with theuser’s property with the determined location information of IoT device301 form location detection device 522. If the location informationmatch, possession determination system 414 can determine the user’sphysical possession of IoT device 301.

In a non-limiting example, possession determination system 414 canperiodically check the location information of IoT device 301 fromlocation detection device 522. If possession determination system 414determines that location information of IoT device 301 does not anymorematch the location information associated with the user of IoT device301, possession determination system 414 can disable IoT device 301. Bydoing so, possession determination system 414 can ensure that IoT device301 is operating in the appropriate environment.

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include proving the user’s knowledge of a passwordassociated with the network to which IoT device 301 is connected to. IoTdevice 301 can be connected to network 303 of FIG. 3 . In a non-limitingexample, network 303 can include, but is not limited to, a WLAN (e.g., aWiFi network) that is protected using a password. In this example, auser can be prompted by IoT device 301 and/or system servers 305 toprovide the password associated with network 303. Possessiondetermination system 414 of IoT device 301 (and/or system servers 305)can compare the entry provided by the user to the password associatedwith network 303. If matched, possession determination system 414 of IoTdevice 301 (and/or system servers 305) can determine the user’s physicalpossession of IoT device 301.

In another example, possession determination system 414 of IoT device301 (and/or system servers 305) can determine that user device 307 isalso connected to network 303 using the password associated with network303. In this example, possession determination system 414 of IoT device301 (and/or system servers 305) can determine that the user has thecorrect password, and therefore, has physical possession of IoT device301.

This example can provide added security when a user tries to take overexisting IoT devices that are in communication with a network (e.g.,using an access point of the network).

According to some embodiments, one approach to prove physical possessionof IoT device 301 can include using one or more cameras and/or one ormore light detection and ranging (lidar) devices of IoT device 301. FIG.5I illustrates a block diagram of possession determination system 414having camera 524 and/or lidar 526, according to some embodiments.Camera 524 and/or lidar 526 can be (or be part of) sensor 402 of FIG. 4, according to some embodiments.

In some examples, possession determination system 414 can use camera 524and image or video recognition methods to detect an image or video froma user to determine the user’s physical possession of IoT device 301. Ina non-limiting example, the user can use its user device 307 to displayan image to IoT device 301. Using camera 524, possession determinationsystem 414 can capture the image, process it, and compare it with apredetermined image (stored in, for example, storage/buffer 408). If thecaptured and predetermined images match, possession determination system414 can determine that the user has physical possession of IoT device301. However, the embodiments of this disclosure are not limited tothese examples and other images and/or videos from the user can be usedto determine the user’s physical possession of IoT device 301.

In some examples, possession determination system 414 can use lidar 526and image, video, or gesture recognition methods to detect, for example,a gesture from a user to determine the user’s physical possession of IoTdevice 301. In a non-limiting example, the user can provide a gesture toIoT device 301. Using lidar 526, possession determination system 414 cancapture the gesture, process it, and compare it with a predeterminedgesture (stored in, for example, storage/buffer 408). If the capturedand predetermined gestures match, possession determination system 414can determine that the user has physical possession of IoT device 301.However, the embodiments of this disclosure are not limited to theseexamples and other gestures from the user can be used to determine theuser’s physical possession of IoT device 301. For example, absence orpresence of an object can be used as the gesture.

In some examples, IoT device 301 and/or system servers 305 can trigger(e.g., by sending a request to) the user and/or the user device todisplay the image, the video, the gesture, or the like.

According to some embodiments, the image, the video, the gesture, or thelike can be based on predetermined information that is shared betweenIoT device 301 and user device 307. In some examples, the predeterminedinformation can be shared between IoT device 301 and user device 307 bysystem server 305. System server 305 can store and manage the useraccount associated with IoT device 301.

Although some exemplary embodiments are discussed above with respect topossession determination system 414 determining the physical possessionof IoT device 301, these embodiments can additionally (or alternatively)be performed by system servers 305. In other words, a user can prove itsphysical possession of IoT device 301 with system servers 305 using, forexample, one or more embodiments discussed above. The user can applyother approaches to establish trust with system servers 305 allowing theuser to take over IoT devices 301. In some examples, to prove itsphysical possession of IoT device 301, user can provide identifyinginformation associated with IoT device 301 to system servers 305. Theidentifying information associated with IoT device 301 can include, butis not limited to, QR code, medium access control (MAC) address, or thelike associated with IoT device 301.

According to some embodiments, a user can identify one or more IoTdevices 301 using, for example, user device 307. In some examples,identifying IoT devices 301 can be used in setting up IoT devices 301,in naming IoT devices 301, in replacing IoT devices 301, in removing IoTdevices 301, in proving physical possession, or the like. In someexamples, user device 307 can include a user interface (UI) forconfiguring, controlling, and/or operating IoT devices 301. For example,user 332 can use the UI of user device 307 to configure, control, and/oroperate IoT devices 301. The UI of user device 307 can be associatedwith the user account of the user of user device 307. In one example,user 332 can use the UI of user device 307 to directly (e.g., throughnetwork 303) configure, control, and/or operate IoT devices 301.Additionally, or alternatively, user 332 can use the UI of user device307 to configure, control, and/or operate IoT devices 301 through systemservers 305.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate and emit light. For example, the user can use theUI of user device 307 to select IoT device 301 a. The selected IoTdevice 301 a can emit light (e.g., using light source 518 of FIG. 5G) toidentify IoT device 301 a.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate or adjust IoT device 301’s output. For example,the user can use the UI of user device 307 to select IoT device 301 a.The selected IoT device 301 a generates and/or changes its associatedoutput (e.g., using actuator 406 of FIG. 4 ) to identify IoT device 301a.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate and transmit packets (e.g., RF packets). Forexample, the user can use the UI of user device 307 to select IoT device301 a. The selected IoT device 301 a generates and transmits the packets(e.g., RF packets) using, for example, transceiver 412 of FIG. 4 and/ortransceiver 504. The user can move user device 307 to receive thepackets to identify IoT device 301 a. In some examples, user device 307can identify IoT device 301 a based on the received power of thereceived packets. However, user device 307 can use other parametersassociated with the received packet to IoT device 301 a.

In one example, identifying IoT device 301 can include using thelocation information of IoT device 301 from, for example, locationdetection device 522. For example, the user can use the UI of userdevice 307 to select IoT device 301 a and view the location informationof IoT device 301 a. In some examples, UI of user device 307 canvisually display the location of IoT device 301 a within, for example,the user’s property.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate and transmit light (e.g., visible light, IRlight, laser, or the like) using, for example, light source 518. Forexample, the user can use the UI of user device 307 to select IoT device301 a. The selected IoT device 301 a generates and transmits light toidentify IoT device 301 a. User device 307 (alone or with a dongle) candetect the transmitted light to identify IoT device 301 a.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate and transmit NFC packets. For example, the usercan use the UI of user device 307 to select IoT device 301 a. Theselected IoT device 301 a generates and transmits the NFC packets using,for example, transceiver 412 of FIG. 4 and/or NFC transceiver 510. Theuser can move user device 307 to receive the NFC packets to identify IoTdevice 301 a. In some examples, user device 307 can identify IoT device301 a based on the received power of the received packets. However, userdevice 307 can use other parameters associated with the received packetto IoT device 301 a.

In one example, identifying IoT device 301 can include triggering IoTdevice 301 to generate and emit sound signals using, for example,speaker 514. For example, the user can use the UI of user device 307 toselect IoT device 301 a. The selected IoT device 301 a can generate andemit sound signals to identify IoT device 301 a.

FIG. 6 illustrates an example method 600 for determining physicalpossession of a plurality of IoT devices, according to some embodiments.As a convenience and not a limitation, FIG. 6 may be described withregard to elements of FIGS. 1-5 . Method 600 may represent the operationof an IoT device (e.g., IoT device 301 of FIGS. 3 and 4 ) and/or asystem server (e.g., system servers 305 of FIG. 3 ) for determiningphysical possession of a plurality of IoT devices. Method 600 may alsobe performed by user device 307 of FIG. 3 , device 106 of FIG. 2 and/orcomputer system 700 of FIG. 7 . But method 600 is not limited to thespecific aspects depicted in those figures and other systems may be usedto perform the method as will be understood by those skilled in the art.It is to be appreciated that not all operations may be needed, and theoperations may not be performed in the same order as shown in FIG. 6 .

According to some embodiments, IoT devices 301 a-301 n can be associatedwith IoT environment 300. IoT devices 301 a-301 n can also be connectedto, and communicate with each other using, network 303 (e.g., a meshnetwork). Method 600 provides an exemplary method where by determiningphysical possession of one or more IoT devices, the physical possessionof the plurality of IoT devices 301 a-301 n can be determined. In otherwords, by determining physical possession of a subset of IoT devices 301a-301 n, the physical possession of the plurality of IoT devices 301a-301 n can be determined. Therefore, if the ownership (e.g., physicalpossession) of IoT devices changes, by determining the physicalpossession of some of the IoT devices, the ownership of the plurality ofIoT devices can be determined/changed. Also, if one or more IoT devicesare added, changed, and/or removed, the ownership (e.g., physicalpossession) of IoT devices can be dynamically determined and/or changed.

At 602, physical possession of a first IoT device of the plurality ofIoT devices is determined. For example, IoT device 301 a and/or systemserver 305 can determine that a user has physical possession over IoTdevice 301 a. In some examples, one or more embodiments discussed abovewith respect to, for example, FIGS. 5A-5I can be used to determine thephysical possession of the first IoT device.

At 604, it is determined whether the first IoT device with thedetermined physical possession (e.g., IoT device 301 a) satisfy acondition. For example, IoT device 301 a and/or system server 305 candetermine whether the first IoT device with the determined physicalpossession (e.g., IoT device 301 a) satisfies the condition.

In one non-limiting example, the condition can include a number of IoTdevices having the same determined physical possession. For example, IoTdevice 301 a and/or system server 305 can determine the number of IoTdevices having the same determined physical possession and can comparethe determined number with a threshold to determine whether thecondition is satisfied. In this example, if a predetermined number ofIoT devices from the plurality of IoT devices have the same determinedphysical possession, it can be determined that the plurality of IoTdevices have the same determined physical possession.

In another non-limiting example, the condition can include physicallocation of the IoT device(s) with the determined physical possession.For example, if the IoT devices are associated with a physical propertyof the user, if the physical possession of one or more IoT devicesinside the physical property is determined, then the determined physicalpossession can be used for the plurality of IoT devices. However, if thephysical possession of one or more IoT devices outside the physicalproperty is determined, then the determined physical possession may notbe used for the plurality of IoT devices.

In some examples, if a number or a percentage of the plurality of IoTdevices with the determined physical possession are inside the physicalproperty, the determined physical possession can be used for theplurality of IoT devices. In this example, determining whether thecondition is satisfied (e.g., operation 604) can include determining thelocation of the IoT devices with the determined physical possession,determining a number of IoT devices that are inside the physicalproperty of the user, and comparing the determined number (or apercentage of the IoT devices inside the physical property compared tothe plurality of IoT devices) with a threshold number (or a thresholdpercentage). If the number (or the percentage) of the IoT devices insidethe physical property of the user is equal or greater than the thresholdnumber (or threshold percentage), then the determined physicalpossession of the IoT devices in the property can be used for theplurality of IoT devices. However, if the number (or the percentage) ofthe IoT devices inside the physical property of the user is less thanthe threshold number (or threshold percentage), then the determinedphysical possession may not be used for the plurality of IoT devices.

In another example, the condition can include whether the subset of theIoT devices are in a secure part of the mesh network of the IoT devices.

In another non-limiting example, the condition can include type(s) ofthe IoT device(s) with the determined physical possession. For example,if the IoT devices are associated with the physical property of theuser, if IoT devices with the determined physical possession are one ormore IoT devices that can be fixed to the physical property, then thedetermined physical possession can be used for the plurality of IoTdevices. However, if IoT devices with the determined physical possessionare one or more IoT devices that can be easily moved, then thedetermined physical possession may not be used for the plurality of IoTdevices. In another example, if IoT devices with the determined physicalpossession are one or more IoT devices that are considered as devices tobe set up inside of the physical property, then the determined physicalpossession can be used for the plurality of IoT devices. However, if IoTdevices with the determined physical possession are one or more IoTdevices that that are considered as devices to be set up outside of thephysical property, then the determined physical possession may not beused for the plurality of IoT devices.

In another non-limiting example, the condition can include usingdifferent type(s) of determining/proving physical possession. Forexample, one or more parameters can be defined for applying thedetermined physical possession of the subset to the plurality of IoTdevice. The one or more parameters can include one or more type(s) ofdetermining/proving physical possession. The types ofdetermining/proving physical possession can include, but are not limitedto, using off/on mechanisms, using QR code, using RF transceiver, usingNFC transceiver, using light signals, using audio signals, using magnet,using accelerometer, or the like.

It is noted that although some exemplary conditions are provided, theembodiments of this disclosure are not limited to these examples, andcan include other conditions.

If it is determined in 604 that the first IoT device with determinedphysical possession (e.g., IoT device 301 a) does not satisfy thecondition, method 600 can move to 608. At 608, physical possession ofanother (e.g., a second) IoT device of the plurality of IoT devices isdetermined. For example, IoT device 301 b and/or system server 305 candetermine that the user has physical possession over IoT device 301 b.In some examples, one or more embodiments discussed above with respectto, for example, FIGS. 5A-5I can be used to determine the physicalpossession of the other IoT device.

After determining the physical possession of the other IoT device (e.g.,IoT device 301 b), method 600 can return to operation 604 to determinewhether the IoT devices (e.g., IoT device 301 a and/or 301 b) withdetermined physical possession satisfy the condition. In some examples,operation 604 can also include determining whether the IoT devices(e.g., IoT devices 301 a and/or 301 b) with determined physicalpossession have the same physical possession. Operations 604 and 608 cancontinue until the condition is satisfied, according to someembodiments.

If it is determined in 604 that the first IoT device with determinedphysical possession (e.g., IoT device 301 a) or the IoT devices (e.g.,IoT devices 301 a and 301 b) with determined physical possession satisfythe condition, method 600 can move to 606. At 606, the physicalpossession of the plurality of IoT devices can be determined based onthe determined physical possession of the one or more IoT devices. Forexample, IoT devices 301 a-301 n and/or system servers 305 can determinethe physical possession of IoT devices 301 a-301 n based on at least onone of the determined possession of IoT device 301 a, the determinedpossession of IoT device 301 b, or the determined possession of IoTdevices 301 a and 301 b. For example, if a number of IoT devices withthe determined physical possession are to satisfy the condition ofoperation 604 to determine the physical possession of the plurality ofIoT devices, the the physical possession of the plurality of IoT devices(e.g., IoT devices 301 a-301 n) can be determined based on thedetermined physical possession of the number of IoT devices (e.g., IoTdevices 301 a and 301 b).

Example Computer System

Various embodiments may be implemented, for example, using one or morewell-known computer systems, such as computer system 700 shown in FIG. 7. For example, the media device 106 may be implemented usingcombinations or sub-combinations of computer system 700. Also oralternatively, one or more computer systems 700 may be used, forexample, to implement any of the embodiments discussed herein, as wellas combinations and sub-combinations thereof.

Computer system 700 may include one or more processors (also calledcentral processing units, or CPUs), such as a processor 704. Processor704 may be connected to a communication infrastructure or bus 706.

Computer system 700 may also include user input/output device(s) 703,such as monitors, keyboards, pointing devices, etc., which maycommunicate with communication infrastructure 706 through userinput/output interface(s) 702.

One or more of processors 704 may be a graphics processing unit (GPU).In an embodiment, a GPU may be a processor that is a specializedelectronic circuit designed to process mathematically intensiveapplications. The GPU may have a parallel structure that is efficientfor parallel processing of large blocks of data, such as mathematicallyintensive data common to computer graphics applications, images, videos,etc.

Computer system 700 may also include a main or primary memory 708, suchas random access memory (RAM). Main memory 708 may include one or morelevels of cache. Main memory 708 may have stored therein control logic(i.e., computer software) and/or data.

Computer system 700 may also include one or more secondary storagedevices or memory 710. Secondary memory 710 may include, for example, ahard disk drive 712 and/or a removable storage device or drive 714.Removable storage drive 714 may be a floppy disk drive, a magnetic tapedrive, a compact disk drive, an optical storage device, tape backupdevice, and/or any other storage device/drive.

Removable storage drive 714 may interact with a removable storage unit718. Removable storage unit 718 may include a computer usable orreadable storage device having stored thereon computer software (controllogic) and/or data. Removable storage unit 718 may be a floppy disk,magnetic tape, compact disk, DVD, optical storage disk, and/ any othercomputer data storage device. Removable storage drive 714 may read fromand/or write to removable storage unit 718.

Secondary memory 710 may include other means, devices, components,instrumentalities or other approaches for allowing computer programsand/or other instructions and/or data to be accessed by computer system700. Such means, devices, components, instrumentalities or otherapproaches may include, for example, a removable storage unit 722 and aninterface 720. Examples of the removable storage unit 722 and theinterface 720 may include a program cartridge and cartridge interface(such as that found in video game devices), a removable memory chip(such as an EPROM or PROM) and associated socket, a memory stick and USBor other port, a memory card and associated memory card slot, and/or anyother removable storage unit and associated interface.

Computer system 700 may further include a communication or networkinterface 724. Communication interface 724 may enable computer system700 to communicate and interact with any combination of externaldevices, external networks, external entities, etc. (individually andcollectively referenced by reference number 728). For example,communication interface 724 may allow computer system 700 to communicatewith external or remote devices 728 over communications path 726, whichmay be wired and/or wireless (or a combination thereof), and which mayinclude any combination of LANs, WANs, the Internet, etc. Control logicand/or data may be transmitted to and from computer system 700 viacommunication path 726.

Computer system 700 may also be any of a personal digital assistant(PDA), desktop workstation, laptop or notebook computer, netbook,tablet, smart phone, smart watch or other wearable, appliance, part ofthe Internet-of-Things, and/or embedded system, to name a fewnon-limiting examples, or any combination thereof.

Computer system 700 may be a client or server, accessing or hosting anyapplications and/or data through any delivery paradigm, including butnot limited to remote or distributed cloud computing solutions; local oron-premises software (“on-premise” cloud-based solutions); “as aservice” models (e.g., content as a service (CaaS), digital content as aservice (DCaaS), software as a service (SaaS), managed software as aservice (MSaaS), platform as a service (PaaS), desktop as a service(DaaS), framework as a service (FaaS), backend as a service (BaaS),mobile backend as a service (MBaaS), infrastructure as a service (IaaS),etc.); and/or a hybrid model including any combination of the foregoingexamples or other services or delivery paradigms.

Any applicable data structures, file formats, and schemas in computersystem 700 may be derived from standards including but not limited toJavaScript Object Notation (JSON), Extensible Markup Language (XML), YetAnother Markup Language (YAML), Extensible Hypertext Markup Language(XHTML), Wireless Markup Language (WML), MessagePack, XML User InterfaceLanguage (XUL), or any other functionally similar representations aloneor in combination. Alternatively, proprietary data structures, formatsor schemas may be used, either exclusively or in combination with knownor open standards.

In some embodiments, a tangible, non-transitory apparatus or article ofmanufacture comprising a tangible, non-transitory computer useable orreadable medium having control logic (software) stored thereon may alsobe referred to herein as a computer program product or program storagedevice. This includes, but is not limited to, computer system 700, mainmemory 708, secondary memory 710, and removable storage units 718 and722, as well as tangible articles of manufacture embodying anycombination of the foregoing. Such control logic, when executed by oneor more data processing devices (such as computer system 700 orprocessor(s) 704), may cause such data processing devices to operate asdescribed herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments of this disclosure using data processing devices, computersystems and/or computer architectures other than that shown in FIG. 7 .In particular, embodiments can operate with software, hardware, and/oroperating system implementations other than those described herein.

Conclusion

It is to be appreciated that the Detailed Description section, and notany other section, is intended to be used to interpret the claims. Othersections can set forth one or more but not all exemplary embodiments ascontemplated by the inventor(s), and thus, are not intended to limitthis disclosure or the appended claims in any way.

While this disclosure describes exemplary embodiments for exemplaryfields and applications, it should be understood that the disclosure isnot limited thereto. Other embodiments and modifications thereto arepossible, and are within the scope and spirit of this disclosure. Forexample, and without limiting the generality of this paragraph,embodiments are not limited to the software, hardware, firmware, and/orentities illustrated in the figures and/or described herein. Further,embodiments (whether or not explicitly described herein) havesignificant utility to fields and applications beyond the examplesdescribed herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments can performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein. Additionally, some embodiments can bedescribed using the expression “coupled” and “connected” along withtheir derivatives. These terms are not necessarily intended as synonymsfor each other. For example, some embodiments can be described using theterms “connected” and/or “coupled” to indicate that two or more elementsare in direct physical or electrical contact with each other. The term“coupled,” however, can also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other.

The breadth and scope of this disclosure should not be limited by any ofthe above-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. An Internet-of-Things (IoT) device, comprising: atransceiver configured to communicate over a wireless network; and aphysical possession determining system configured to determine physicalpossession of the IoT device by at least one of: transmitting a firstsignal to a user device, the first signal generated based onpredetermined information shared between the IoT device and the userdevice; or receiving a second signal from the user device, the secondsignal generated based on the predetermined information shared betweenthe IoT device and the user device.
 2. The IoT device of claim 1,further comprising: a magnetic detector configured to detect a presenceof a magnet to determine the physical possession of the IoT device. 3.The IoT device of claim 1, wherein: the first signal comprises a firstradio frequency (RF) packet, the second signal comprises a second RFpacket, and the physical possession determining system is configured todetermine the physical possession of the IoT device based on the secondRF packet received from the user device.
 4. The IoT device of claim 1,wherein: the second signal comprises at least one of an audio signal, avisible light signal, an infrared light signal, or a laser signal, andthe physical possession determining system is further configured to:determine information associated with the second signal; compare theinformation associated with the second signal with the predeterminedinformation; and determine the physical possession of the IoT devicebased on the information associated with the second signal matching withthe predetermined information.
 5. The IoT device of claim 1, furthercomprising: one or more buttons, wherein the physical possessiondetermining system is configured to: determine that the one or morebuttons are actuated in a predetermined manner; and determine thephysical possession of the IoT device based on the determination thatthe one or more buttons are actuated in the predetermined manner.
 6. TheIoT device of claim 1, further comprising: a location detection deviceconfigured to determine location information associated with the IoTdevice, wherein the physical possession determining system is configuredto: determine location information associated with a user associatedwith the IoT device; compare the location information associated withthe IoT device and the location information associated with the user;and determine the physical possession of the IoT device in response tothe location information associated with the IoT device matching thelocation information associated with the user.
 7. The IoT device ofclaim 1, wherein the physical possession determining system isconfigured to: determine that a power supply associated with the IoTdevice turned off and on in a predetermined manner; and determine thephysical possession of the IoT device in response to the determinationthat the power supply associated with the IoT device turned off and onin the predetermined manner.
 8. The IoT device of claim 1, wherein thephysical possession determining system is configured to: receive arequest for identifying the IoT device; and activate at least one of alight source of the IoT device, a speaker of the IoT device, anear-field communication (NFC) transceiver of the IoT device, or a radiofrequency (RF) transceiver of the IoT device.
 9. The IoT device of claim1, further comprising: a microphone configured to receive the secondsignal, the second signal comprising an audio signal, wherein thephysical possession determining system is further configured to:determine information associated with the audio signal; compare theinformation associated with the audio signal with the predeterminedinformation; and determine the physical possession of the IoT devicebased on the information associated with the audio signal matching withthe predetermined information.
 10. The IoT device of claim 1, furthercomprising: a speaker configured to transmit the first signal, the firstsignal comprising an audio signal, wherein the physical possessiondetermining system is further configured to: receive the second signal,the second signal comprising a message indicating that informationassociated with the audio signal match the predetermined information;and determine the physical possession of the IoT device based on thesecond signal.
 11. The IoT device of claim 1, further comprising: alight sensor configured to receive the second signal, the second signalcomprising a visible light signal, an infrared light signal, or a lasersignal, wherein the physical possession determining system is furtherconfigured to: determine information associated with the visible lightsignal, the infrared light signal, or the laser signal; compare theinformation associated with the visible light signal, the infrared lightsignal, or the laser signal with the predetermined information; anddetermine the physical possession of the IoT device based on theinformation associated with the visible light signal, the infrared lightsignal, or the laser signal matching with the predetermined information.12. An Internet-of-Things (IoT) device, comprising: a transceiverconfigured to communicate over a wireless network; and a physicalpossession determining system configured to determine physicalpossession of the IoT device by: transmitting a first signal to a userdevice, the first signal generated based on predetermined informationshared between the IoT device and the user device; and receiving asecond signal from the user device, the second signal generated based onthe predetermined information shared between the IoT device and the userdevice.
 13. The IoT device of claim 12, further comprising: a magneticdetector configured to detect a presence of a magnet to determine thephysical possession of the IoT device.
 14. The IoT device of claim 12,wherein: the first signal comprises a first radio frequency (RF) packet,the second signal comprises a second RF packet, and the physicalpossession determining system is configured to determine the physicalpossession of the IoT device based on the second RF packet received fromthe user device.
 15. The IoT device of claim 12, further comprising: amicrophone configured to receive the second signal, the second signalcomprising an audio signal, wherein the physical possession determiningsystem is further configured to: determine information associated withthe audio signal; compare the information associated with the audiosignal with the predetermined information; and determine the physicalpossession of the IoT device based on the information associated withthe audio signal matching with the predetermined information.
 16. TheIoT device of claim 12, further comprising: a speaker configured totransmit the first signal, the first signal comprising an audio signal,wherein the physical possession determining system is further configuredto: receive the second signal, the second signal comprising a messageindicating that information associated with the audio signal match thepredetermined information; and determine the physical possession of theIoT device based on the second signal.
 17. The IoT device of claim 12,further comprising: a light sensor configured to receive the secondsignal, the second signal comprising a visible light signal, an infraredlight signal, or a laser signal, wherein the physical possessiondetermining system is further configured to: determine informationassociated with the visible light signal, the infrared light signal, orthe laser signal; compare the information associated with the visiblelight signal, the infrared light signal, or the laser with thepredetermined information; and determine the physical possession of theIoT device based on the information associated with the visible lightsignal, the infrared light signal, or the laser signal matching with thepredetermined information.
 18. The IoT device of claim 12, furthercomprising: a light source configured to transmit the first signal, thefirst signal comprising a visible light signal, an infrared lightsignal, or a laser signal, wherein the physical possession determiningsystem is further configured to: receive the second signal, the secondsignal comprising information associated with the visible light signal,the infrared light signal, or the laser signal; and determine thephysical possession of the IoT device based on the second signal. 19.The IoT device of claim 12, further comprising: a light sourceconfigured to transmit the first signal, the first signal comprising avisible light signal, an infrared light signal, or a laser signal; and alight sensor configured to receive the second signal, the second signalcomprising a reflected signal as a reflection of the visible lightsignal, the infrared light signal, or the laser signal, wherein thephysical possession determining system is further configured to:determine information associated with the reflected signal; compare theinformation associated with the audio signal with the predeterminedinformation; and determine the physical possession of the IoT devicebased on the information associated with the reflected signal matchingwith the predetermined information.
 20. An Internet-of-Things (IoT)device, comprising: a transceiver configured to communicate over awireless network; and a physical possession determining systemconfigured to determine physical possession of the IoT device by:transmitting a first signal to a user device, the first signal generatedbased on predetermined information shared between the IoT device and theuser device, wherein the first signal comprises at least one of a firstradio frequency (RF) packet, a first audio signal, a first visible lightsignal, a first infrared light signal, or a first laser signal; andreceiving a second signal from the user device, the second signalgenerated based on the predetermined information shared between the IoTdevice and the user device, wherein the second signal comprises at leastone of a second RF packet, a second audio signal, a second visible lightsignal, a second infrared light signal, or a second laser signal.